Disconnect logic to fill in role parents #15462
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
For code removals after RBAC changes, this is my first pass, since it is the most mechanistic change.
A role (in the old system) has both parent roles and ancestor roles tracked in relationships. We have already disconnected the logic for rebuilding ancestors but rebuilding parents is more minimal... although still maintained via connected signals.
The goal of this PR is to gut the signals for role parent rebuilding. This gets weird in a few cases, like how editing related ForeignKey fields can change role parents. I want to also be thorough about tracing de-referenced methods and deleting them.
ping @hakbailey
ISSUE TYPE
COMPONENT NAME